Topology discovery of a private network

ABSTRACT

The present invention relates to a method and system for determining devices connected to a private network through a gateway. A Network Management System (NMS) through the use of inquiries and Port Address Translation (PAT) commands is able to determine the topology of the network of devices within a private network and thus communicate with them. This is achieved through the use of Port Address Translation (PAT) initiated by the NMS to set a port for each device connected to the gateway.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of pending U.S. patent application Ser. No. 11/355,730, filed Feb. 15, 2006, the disclosure of which is incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to the discovery of the topology of a private network by a Network Management System (NMS) when the NMS is not directly connected to the private network.

BACKGROUND OF THE INVENTION

Through the use of the Simple Network Management Protocol (SNMP) and other discovery protocols such as Cisco Discovery Protocol (CDP), it is possible for a Network Management System (NMS) to discover the topology of a network. However, there is a limitation in such an approach as the devices in the network cannot be discovered if they are on a private network as defined by RFC 1918 of the Internet Engineering Task Force (IETF).

The present invention addresses the need for a system and method for discovering the devices within a private network by an NMS not contained within the private network.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention, and to show more clearly how it may be carried into effect, reference will now be made, by way of example, to the accompanying drawings which aid in understanding an embodiment of the present invention and in which:

FIG. 1 is a block diagram illustrating an example of a computer network;

FIG. 2 is a block diagram of an NMS;

FIG. 3 is a flowchart of a prior art discovery process;

FIG. 4 is a flowchart of an embodiment of a discovery process; and

FIG. 5, a block diagram illustrating the logical flow for the mitigation of security risks.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

For the purpose of describing the prior art means of discovering the topology of a network as well as how an embodiment of the present invention achieves this task we refer first to FIG. 1. FIG. 1 is a block diagram illustrating an example of a computer network and is shown generally as 10.

Network 10 includes a public network 12 connected to a gateway router 14 via an example IP address of 171.69.2.1, shown as feature 16. Gateway router 14 is further connected to a private network 18 via an example IP address of 192.168.1.1, shown as feature 20.

Gateway router 14 acts as a gateway between public network 12 and private network 18. In one embodiment gateway router 14 is a Network Address Translation/Port Address Translation (NAT/PAT) router. NAT/PAT allows a router to rewrite any of the source addresses, destination addresses or ports of IP packets as the pass through the router. Typically this is done to allow devices connected to private network 18 to utilize a single IP address (feature 16) to connect to public network 12. Examples of a private network 18 include a Local Area Network (LAN) and a Wide Area Network (WAN). These private networks 18 are established by an organization that wishes to avoid direct connection between devices in private network 18 and public network 12.

Network Management System (NMS) 22 is connected to public network 12. NMS 22 serves to monitor and provide services to and from the devices connected to public network 12. Part of the function of NMS 22 is to discover and connect to devices through public network 12. By way of example, the devices shown in FIG. 1 are: SwitchA (24), RouterA (26) and Access Point (AP 28). AP 28 is a device that communicates with wireless clients having access to private network 18. As devices 24, 26 and 28 are within private network 18, NMS 22 is unable to discover them.

We now refer to FIG. 2 a block diagram of an NMS 22. The components of NMS 22 are simply examples of how a generic computing device may be configured to implement NMS 22. NMS 22 comprises one or more processors 30 a to 30 n. Each processor 30 a to 30 n is capable of running computing instructions to execute the functions as described with regard to embodiments of the present invention. Memory 32 provides temporary or permanent storage for instructions and data required by processors 30 a to 30 n. Network interface 34 serves to connect NMS 22 to public network 12 through the use of a communication protocol of choice, an example of which would be TCP/IP or Ethernet. Database controller 36 serves to allow processors 30 a to 30 n to store and retrieve information regarding private networks 18 and gateway routers 14 to and from NMS database 38. Communications bus 40 allows for communication between the components of NMS 22, namely processors 30 a to 30 n, memory 32, network interface 34 and database controller 36.

To illustrate the problem of discovering devices within private network 18 by NMS 22 we now refer to FIG. 3, a flowchart of a prior art discovery process.

Beginning at step 50, NMS 22 discovers gateway router 14 with an example IP address of 171.69.2.1 (feature 16 of FIG. 1). At step 52 NMS 22 sends a Simple Network Management Protocol (SNMP) request message to gateway router 14 to obtain information about devices connected to gateway router 14. At step 54 gateway router 14 informs NMS 22 that it is connected to SwitchA 24. At step 56 NMS 22 sends an SNMP request to SwitchA 24 via example IP address 192.168.1.1, to obtain information about devices connected to SwitchA 24. The request sent at step 56 will eventually timeout at step 58 as SwitchA 24 is within private network 18 and as such cannot provide information on RouterA 26 and AP 28.

Referring now to FIG. 4 a flowchart of an embodiment of a discovery process as implemented by the present invention is shown.

Beginning at step 60 NMS 22 discovers gateway router 14 with an example IP address of 171.69.2.1. At step 62 NMS 22 sends a Simple Network Management Protocol (SNMP) message to gateway router 14 to obtain information about devices connected to gateway router 14. At step 64 gateway router 14 informs NMS 22 that it is connected to SwitchA 24. From the information returned at step 64 NMS 22 is aware that SwitchA 24 is a private address. At this point processing moves to step 68 but an alternative embodiment may be utilized as shown in step 66. In an alternative embodiment if NMS 22 determines that SwitchA 24 has a private address it may choose to check whether the private address is accessible or not. This can be done by sending a ping or SNMP message to the private address of SwitchA 24. If the private address of SwitchA 24 is reachable, the NMS 22 may chose to communicate directly with SwitchA 24 and avoid step 68 by moving directly to step 70. At step 68 NMS 22 utilizes telnet/ssh to establish a static PAT entry for SwitchA 24 with gateway router 14. This is done via the following example PAT command, this example is specific to Cisco Internetwork Operating System, other manufacturers may use a different syntax.

ip nat inside source static udp 192.168.1.2 161 171.69.2.1 10000

This now permits NMS 22 to reach SwitchA 24 by sending an SNMP request to gateway router 14 (171.69.2.1) port 10000, as shown in step 70.

At step 72 SwitchA 24 returns information on its neighbors RouterA 26 and AP 28 to NMS 22. At step 74 NMS 22 utilizes telnet/ssh to establish static PAT entries for RouterA 26 and AP 28 with gateway router 14. This is done via the following example PAT commands:

ip nat inside source static udp 192.168.1.3 161 171.69.2.1 10001

ip nat inside source static udp 192.168.1.4 161 171.69.2.1 10002

The steps 64 to 74 are then repeated for RouterA 26 and AP 28 and their neighbors until all devices behind private network 18 are discovered.

The process described with reference to FIG. 4 also allows for the addition of services to the devices connected to private network 18. For example to add ssh services to SwitchA 24, RouterA 26 and AP 28 the following example PAT commands may be used:

ip nat inside source static tcp 192.168.1.2 22 171.69.2.1 20000

ip nat inside source static tcp 192.168.1.3 22 171.69.2.1 20001

ip nat inside source static tcp 192.168.1.4 22 171.69.2.1 20002

Similarly to add telenet services to SwitchA 24, Router A 26 and AP 28 the following example PAT commands may be used:

ip nat inside source static tcp 192.168.1.2 23 171.69.2.1 30000

ip nat inside source static tcp 192.168.1.3 23 171.69.2.1 30001

ip nat inside source static tcp 192.168.1.4 23 171.69.2.1 30002

The IP addresses and PAT commands mentioned in this description apply equally to any version of IP, such as IPv4 and IPv6 as defined by the Internet Engineering Task Force (IETF) in RFC numbers 791, 2373 and 2374.

The references to specific IP addresses are meant only as examples of how an embodiment of the present invention may be utilized. The example disclosed uses a gateway router 14 but applies equally to any device that acts as a gateway between public network 12 and private network 18.

The present invention provides for the opening of ports on a private network 18 to a public network 12. Providing this functionality does provide security risks. These security risks may be mitigated in several ways. We refer now to FIG. 5, a block diagram illustrating the logical flow for the mitigation of security risks. Any of the steps described with reference to FIG. 5 may be implemented individually or in combination.

At step 80 gateway router 14 may set the value of the SNMP community string to a value other than the default of “public”. The SNMP community string is a password like string in an SNMP message. When gateway router 14 receives an SNMP message from NMS 22 it will check the community string to determine if it matches the community string configured for gateway router 14. If it does not match, gateway router 14 will ignore the message.

At step 82 gateway router 14 may configure an access control list and a command authorization list. The access control list would only permit access from NMS 22 and the administrators of gateway router 14. The command authorization list would allow only a limited set of commands to be accepted from NMS 22.

At step 84, NMS 22 removes PAT entries on gateway router 14 after discovery of the devices in private network 18. NMS 22 utilizes NMS database 38 to map the discovered device to its PAT entry.

Another issue to consider in implementing the present invention is the selection of an unused port number to configure a PAT on gateway router 14 for NMS 22 to access devices within private network 18. The inventors propose three methods for doing this. In the first method NMS 22 defines an infrequently used port range for PAT to reduce the collision of ports. For example, a port range of 50,000 to 59,999. This method does not eliminate the collision of ports but does mitigate the possibility. In the second method when NMS 22 is configuring a PAT on gateway router 14 it can examine the NAT/PAT translation table maintained by gateway router 14. By examining the table NMS 22 can select a port from a range which is not in use. However, this requires transfer of the table from gateway router 14 to NMS 22 which consumes network and processor time. Further another process may bind to the port eventually selected while the transfer and examination of the table is being made. The third method is the most robust. In this embodiment a secondary public IP address is configured to the public interface 16 of gateway router 14. This secondary address is solely for the use of NMS 22 to configure PAT. When NMS 22 discovers that gateway router 14 has configured this second address by any number of means, for example by parsing the configuration of gateway router 14, it will use the secondary address and an unassigned number from an infrequently used port range to configure PAT. Since this secondary address will be used only by NMS 22 there are no port collision issues.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. 

1. A gateway device comprising: a public interface associated with a primary public Internet Protocol (IP), address discoverable by other network devices and a secondary public IP address, wherein the secondary public IP address is particularly for discovery by a Network Management Server (NMS); and one or more processors, wherein the one or more processors are configured to: receive a discovery request from the NMS transmitted to the primary public IP address, the discovery request including a request to identify one or more devices of a private network, wherein the NMS is not in the private network; identify a private IP address for each of the one or more devices to the NMS; and responsive to a request from the NMS to add a Port Address Translation (PAT) entry for each of the one or more devices, generate a PAT table corresponding to the secondary public IP address, wherein the request designates a corresponding port for communication with each of the one or more devices selected from unassigned ports and wherein PAT entries include the private IP addresses and corresponding designated ports.
 2. The gateway device of claim 1, wherein the one or more processors are further configured to search an access control list or a command authorization list, or combinations thereof upon receipt of a discovery request from the NMS.
 3. The gateway device of claim 2, wherein the one or more processors are further configured to permit access only to NMS identified in the access control list or authorized administrators of the gateway device or combinations thereof.
 4. The gateway device of claim 3, wherein the one or more processors are further configured to permit commands from the NMS only if the commands are listed in the command authorization list.
 5. The gateway device of claim 1, wherein the one or more processors are further configured to compare a first community string value with a second community string value, wherein the second community string value is received in the discovery request.
 6. The gateway device of claim 5, wherein if the first community string value and the second community string value do not match, the gateway device ignores the discovery request.
 7. A method comprising: discovering a gateway device, wherein the gateway device is in communication with a private network; sending a first Simple Network Management Protocol (SNMP) message to the gateway device, wherein the first SNMP message is configured to elicit information about other devices connected to the gateway device; receiving a message from the gateway device indicating that the gateway device is connected to a private network device; deducing from the message that the private network device is part of the private network and has a private address; and sending a command to the gateway device to establish a static PAT entry corresponding to the private network device on the gateway device designate a first port for communication with the private network device.
 8. The method of claim 7, further comprising: sending a second SNMP message to the gateway device, wherein the second SNMP message is configured to communicate with the private network device for requesting information associated with other private network devices in the private network; responsive to the second SNMP message, receiving information from the private network device associated with at least one of the other private network devices; and sending a second command to the gateway device to establish a second static PAT entry corresponding to the private network device on the gateway device and to designate a second port for communication with the at least one other private network device.
 9. The method of claim 8, further comprising determining that the private network address is accessible, wherein if the private address is accessible then requesting information associated with the other private network devices in the private network.
 10. The method of claim 9, further comprising sending a ping or third SNMP message to the private address of the private network device to determine if the private network device is reachable.
 11. The method of claim 8, wherein the other private network devices are in communication with the private network device.
 12. The method of claim 8, wherein the other private network devices are neighboring the private network device
 13. The method of claim 8, further comprising sending a third command to remove one or more static PAT entries on the gateway device subsequent to discovery of the at least one of the other private network devices.
 14. The method of claim 8, further comprising mapping the discovered private network device and at least one of the other private network devices in a database.
 15. The method of claim 8, further comprising identifying an infrequently used port range and selecting the first designated port and the second designated port from the infrequently used port range.
 16. The method of claim 8, further comprising: accessing a port address table received from the gateway device; identifying ports that are currently unused from the table; and selecting the first designated port and the second designated port from the identified unused ports.
 17. The method of claim 8, further comprising determining whether the gateway device is configured with a secondary public IP address, wherein the secondary address is for use of an NMS.
 18. The method of claim 17, wherein if the NMS discovers that the gateway device is configured with the second public IP address then using the secondary address and an unassigned number from an infrequently used port range to configure PAT.
 19. An apparatus comprising: means for receiving a discovery request from a Network Management System (NMS), wherein the discovery request includes a request to identify a first device of a private network, and wherein the NMS is not part of the private network; means for identifying the first device; means for transmitting a first private IP address for the first device to the NMS; means for receiving an access request from the NMS to add a first Port Address Translation (PAT) entry for the first device, wherein the access request includes the first private IP address and designates a first port for communication with the first device; means for receiving a second discovery request from the NMS to identify a second device of the private network known by the first device; means for identifying the second device; means receiving a second access request for adding add a second PAT entry for the second device, wherein the access request includes a second private IP address and designates a second port for communication with the second device; means for adding the first PAT entry and the second PAT entry to a translation table, wherein the first PAT entry and the second PAT entry include respective the first private IP address and the second private IP address and respective the first designated port and the second designated port; means for communicating the translation table to the NMS; and means for removing the PAT entries.
 20. The apparatus of claim 19, wherein the first and second access requests are accompanied by a password, and further comprising means for verifying the passwords prior to adding the first and second PAT entries to a translation table. 